This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: JavaScript Web APIs, Mobile Web.
Completed Work
W3C Recommendations have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the W3C Recommendation
Track.
Group Notes are not standards and do not
have the same level of W3C endorsement.
Standards
|
2010-12-14
|
translations
·
errata
This document specifies best practices for the development and delivery of Web applications on mobile devices.
|
Group Notes
|
2011-03-17
|
This document defines requirements for controlling access to device APIs, illustrated by corresponding use cases.
|
|
2010-06-29
|
This document provides definitions, use cases, and requirements for making device APIs more privacy-friendly.
|
|
2009-10-15
|
These are the requirements intended to be met in the development of client-side APIs that enable the creation of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc.
|
|
2008-05-30
|
Offline Web Applications highlights the features in HTML 5 that address the challenge of building Web applications that work while offline.
|
Drafts
Below are draft documents:
Proposed Recommendations, Candidate Recommendations, Last Call Drafts, other Working Drafts.
Some of these may become Web Standards through the W3C Recommendation Track
process. Others may be published as Group Notes or
become obsolete specifications.
Proposed Recommendations
|
2012-05-10
|
This specification defines an API that provides Web pages scripted access to geographical location information associated with the hosting device.
|
Candidate Recommendations
|
2013-05-09
|
This specification defines HTML form enhancements that provide access
to the audio, image and video capture capabilities of the device.
|
|
2012-09-20
|
This specification defines an API that enables Web pages to use the Web Sockets protocol for two-way communication with a remote host.
|
|
2012-05-01
|
This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism.
|
Last Call Drafts
|
2013-05-16
|
This document defines APIs for a database of records holding simple values and hierarchical objects.
|
|
2013-04-11
|
This specification defines a client-side API to access metadata information related to media resources on the Web.
|
|
2011-12-01
|
This specification adds the ability to retrieve a civic address,
rather than coordinates, to the Geolocation API.
|
Other Working Drafts
|
2013-03-07
|
A system level API for managing the user's contacts that are stored in the
system's address book.
|
|
2012-12-06
|
The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server, one of the core components of “AJAX”.
|
|
2012-10-25
|
This specification provides an API for representing file objects in web applications, as well as programmatically selecting them and accessing their data.
|
|
2012-07-12
|
This specification defines an API that provides
access to a user’s unified address book.
|
|
2012-03-06
|
This document collates the scenarios that are target use cases
for the Media Capture API that enables access to media input
capabilities for Web applications using Javascript.
|
|
2011-04-14
|
This specification defines an API that provides access to messaging
functionality in the device, including SMS, MMS and email.
|
|
2010-10-05
|
This document identifies the permissions that are needed to use
specific client-side APIs which grant access to sensitive data and
operations.
|
|
2010-02-02
|
This specification defines an API to provide Web applications with access to various hardware properties of the system which they are running on, including battery status, current network bandwidth.
|
Obsolete Specifications
These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.
Retired
|
2011-03-29
|
This document defines APIs for off-line serving of requests to HTTP resources using static and dynamic responses. It extends the function of application caches defined in HTML5.
|
W3C
